Validating data for integration

ABSTRACT

Systems, methods, and non-transitory computer readable media are provided for validating data for integration. A file to be integrated into a dataset may be determined. The file may be characterized by a file name and metadata. Whether the dataset can be identified based on the file name and the metadata may be determined. Based on the dataset not being identifiable, information needed to identify the dataset may be requested. Based on the dataset being identifiable, the file may be routed for integration into the dataset.

FIELD OF THE INVENTION

This disclosure relates to validating data for integration intodatasets.

BACKGROUND

Under conventional approaches, various types of data may be obtained forintegration into particular datasets. Different types of data mayrequire different types of data transformations (e.g., extraction,processing, manipulation, modification, enhancement, combination) to beintegrated into particular datasets. Validating data for integrationinto particular datasets may ensure that the data is routed properly toappropriate datasets.

SUMMARY

Various embodiments of the present disclosure may include systems,methods, and non-transitory computer readable media configured tovalidate data for integration. A file to be integrated into a datasetmay be determined. The file may be characterized by a file name andmetadata. Whether the dataset can be identified based on the file nameand the metadata may be determined. Responsive to the dataset not beingidentifiable, information needed to identify the dataset may berequested. Responsive to the dataset being identifiable, the file may berouted for integration into the dataset.

In some embodiments, at least some of the metadata may be identifiedbased on parsing the file name. In some embodiments, the file mayinclude binary data, and at least some of the metadata may be identifiedbased on decoding a portion of the binary data.

In some embodiments, requesting the information needed to identify thedataset may include displaying the information needed to identify thedataset within a file integration interface. In some embodiments, thefile integration interface may provide a preview of the file. In someembodiments, the file integration interface may provide a view ofinformation used to identify the dataset. In some embodiments, the fileintegration interface may enable a user to change the information usedto identify the dataset.

These and other features of the systems, methods, and non-transitorycomputer readable media disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this specification, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for purposes ofillustration and description only and are not intended as a definitionof the limits of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain features of various embodiments of the present technology areset forth with particularity in the appended claims. A betterunderstanding of the features and advantages of the technology will beobtained by reference to the following detailed description that setsforth illustrative embodiments, in which the principles of the inventionare utilized, and the accompanying drawings of which:

FIG. 1 illustrates an example environment for validating data forintegration, in accordance with various embodiments.

FIG. 2 illustrates an example file naming convention for validating datafor integration, in accordance with various embodiments.

FIG. 3 illustrates an example user interface for validating data forintegration, in accordance with various embodiments.

FIG. 4 illustrates a flowchart of an example method, in accordance withvarious embodiments.

FIG. 5 illustrates a block diagram of an example computer system inwhich any of the embodiments described herein may be implemented.

DETAILED DESCRIPTION

A claimed solution rooted in computer technology overcomes problemsspecifically arising in the realm of computer technology. In variousimplementations, a computing system may determine (e.g., based on userupload, system download) a file to be integrated into a dataset. Thefile may be characterized by a file name and metadata. In someembodiments, at least some of the metadata may be identified byprocessing other information. For example, at least some of the metadatamay be identified based on parsing the file name. As another example,the file may include binary data, and at least some of the metadata maybe identified based on decoding a portion of the binary data. Thecomputing system may determine whether the dataset can be identifiedbased on the file name and the metadata. Based on the dataset not beingidentifiable, the computing system may request information needed toidentify the dataset. Requesting the information needed to identify thedataset may include displaying such information within a fileintegration interface. The file integration interface may provide otherfunctionalities, such as receiving the file to be integrated into adataset (e.g., via drag and drop of the file into the interface, viaadding option in the interface), providing a preview of the file (e.g.,preview of a binary file based on partial decoding), providing a view ofinformation used to identify the dataset, and/or enabling a user tochange the information used to identify the dataset. Based on thedataset being identifiable, the computing system may route the file forintegration into the dataset. For example, the file integrationinterface may provide an option for a user to process/route a singlefile or multiple files (batch processing) for integration into theappropriate dataset(s).

The approach disclosed herein enables input validation for data beforethe data is integrated/routed for integration into a dataset. Inputvalidation may prevent users from integrating improper data intodatasets. Input validation may ensure that a file that is received by acomputing system for integration into a dataset conforms to one or morevalidation rules. Validation rules may be based on one or more of filetype/format, file name/file naming convention, presence of particularmetadata, and/or other information. Validation rules may provide formultiple routing of files/data for integration into different datasets.The approach disclosed herein enables user input to receive informationfor input validation, categorization of different files/raw sources fromwhich integration pipelines may be built, and transparent routing ofdata to appropriate dataset(s).

FIG. 1 illustrates an example environment 100 for validating data forintegration, in accordance with various embodiments. The exampleenvironment 100 may include a computing system 102. The computing system102 may include one or more processors and memory (e.g., permanentmemory, temporary memory). The processor(s) may be configured to performvarious operations by interpreting machine-readable instructions storedin the memory. As shown in FIG. 1, in various embodiments, the computingsystem 102 may include a file engine 112, a dataset engine 114, arequest engine 116, and a routing engine 118. The environment 100 mayalso include one or more datastores that is accessible to the computingsystem 102 (e.g., via one or more network(s)). In some embodiments, thedatastore(s) may include various databases, application functionalities,application/data packages, and/or other data that are available fordownload, installation, and/or execution. While the computing system 102is shown in FIG. 1 as a single entity, this is merely for ease ofreference and is not meant to be limiting. One or morecomponents/functionalities of the computing system 102 described hereinmay be implemented in a single computing device or multiple computingdevices.

In various embodiments, the file engine 112 may be configured todetermine a file to be integrated into one or more datasets. A datasetmay refer to a collection of information that includes multiple dataelements organized into a particular structure and/or using a particularformat. A dataset may be included within a database or multipledatabases. Data elements of a dataset may be accessed individually or incombination by a data analysis platform. A data analysis platform mayrefer to hardware/software components configured to provide analysiscapabilities for data (e.g., database analysis tool). A data analysisplatform may require data (e.g., data elements, datasets) to be storedusing a particular structure/format and/or include one or moreparticular types of information.

A file to be integrated into the dataset may be determined (e.g.,identified) by the file engine 112 based on reception/identification ofthe file by the computing system 102 and/or reception/identification ofthe file by a network/server/computing device monitored by the computingsystem 102. For example, a user may upload a given file to the computingsystem 102 or a network/server/computing device monitored by thecomputing system 102 via an interface (e.g., a file integrationinterface) that receives inputs (e.g., via an upload/import button, viadrag-and-drop) for a dataset/data analysis platform. The file engine 112may determine that the given file is to be integrated into a datasetbased on the user's use of the interface to upload the given file. Asanother example, a user may use the computing system 102 or anetwork/server/computing device monitored by the computing system 102 toselect a particular file for integration into a dataset. The file engine112 may determine that a particular file is to be integrated into adataset based on the user's selection of the particular file.

In some embodiments, a file to be integrated into a dataset may includean archive file. An archive file may refer to a file that includes acollection multiple files in a single file (e.g., zip file, rar file, 7zfile, tar file, jar file, war file). An archive file may provide forconcatenation of files, compression of files, encryption of files, errordetection of files, self-extraction of files, and/or other operationsrelating to archiving of files. An archive file may include information(e.g., metadata) relating to the files within the archive file and/orhow the files within the archive file may be extracted.

In some embodiments, the file engine 112 may be configured to determinethat a file to be integrated into a dataset is an archive file. The fileengine 112 may determine that the file is an archive file based on fileformat (e.g., file extension), analysis of the file (e.g., analysis ofstructure, pattern within the file), user input (e.g., user indicationthat the file is an archive file during file upload/selection forintegration), information (e.g., metadata) relating to the file, and/orother information. Based on the file to be integrated into a datasetbeing an archive file, the file engine 112 may extract the files withinthe archive file for integration into one or more datasets.

A file to be ingested into a dataset may be characterized by a filename, metadata, and/or other information. Information contained withinthe file name and/or metadata may be used to identify the dataset(s) towhich the file is to be integrated. A file name may refer to anidentifier/identifying name of the file. A file name may be required toconform to one or more particular file naming conventions. A file namingconvention may provide a framework for naming a file to describe datacontained within the file, how the file relates to other files, and/orother information which may be used to identify the dataset(s) to whichthe file is to be integrated. For example, a file naming convention mayrestrict the length of a file name and/or provide for the types ofcharacters which may be allowed within the file name. For example, afile name of a file to be ingested into a dataset may be limited to aparticular or ranges of lengths. As another example, certain types ofcharacters may be required/not allowed within one or more portions ofthe file name.

Metadata may refer to one or more sets of data that describes and/orprovides information about the file. Metadata may be contained withinthe file and/or with one or more other files associated with the file.In some embodiments, metadata may be contained within the file name.Including metadata within the file name may enable efficient provisionof information about the dataset(s) to which the file is to beintegrated, such as for files for which metadata in addition to the file(e.g., appending metadata to a portion of the file) may be difficult toprovide and/or not desired. For example, the file to be integrated mayinclude binary data and the file name of the binary data may provideinformation to identify the dataset(s) to which the binary data is to beintegrated.

For example, a file to be integrated may include binary data output byone or more sensors. The file name of the file may be formatted toinclude information about the file, such as the type/format of the data(e.g., type/format of sensor data), specifics relating to the data(e.g., sub-type, sensor channel), location(s) of the data, object(s) towhich the data relates, date(s)/time(s) of the data, user/organization,and/or other information which may be used to identify the dataset(s) towhich the file is to be integrated. In some embodiments, the format ofthe file (e.g., whether the file includes/is included within an archivefile) may be used to identify the dataset(s) to which the file is to beintegrated.

In some embodiments, one or more metadata/characteristics/properties ofthe file relating to its integration into a dataset may be defined whenthe user uploads/selects the file for integration. For example, the usermay define one or more metadata/characteristics/properties of the filewhen uploading the file through an interface (e.g., a file integrationinterface). Such information may be used to determine that the file isto be integrated into a dataset and/or identify the dataset to which thefile is to be integrated.

In various embodiments, the dataset engine 114 may be configured todetermine whether the dataset(s) to which the file is to be integratedcan be identified. Determining whether the dataset(s) to which the fileis to be integrated can be identified may include determining whethersufficient information is included in the file name, the metadata,and/or other information associated with the file. Determining whetherthe dataset(s) to which the file is to be integrated can be identifiedmay include attempting to identify such dataset(s). Responsive to thedataset(s) being identified, it may be determined that the dataset(s)can be identified. Responsive to the dataset(s) not being identified, itmay be determined that the dataset(s) cannot be identified

The dataset(s) to which the file is to be integrated may be identifiedbased on the file name, the metadata, and/or other information.Determining whether the dataset(s) to which the file is to be integratedcan be identified may provide input validation for files. Inputvalidation may prevent users from integrating improper data into one ormore datasets, which may be reserved for one or more specific purposes.Input validation may ensure that a file that is received by a computingsystem for integration into a dataset conforms to one or more validationrules. Validation rules may be based on one or more of file type/format,file name/file naming convention, presence of metadata, and/or otherinformation. Validation rules may provide for multiple routing offiles/data for integration into one or more datasets. Based on differentvalidation rules being met (e.g., by file name, metadata extracted fromthe file/file name), different destinations (particular dataset(s)) fordifferent files may be determined. Application of validation rules to afile may be determined at once (e.g., a single/combined processing todetermine whether the dataset(s) may be identified) or through stages(e.g., multi-pass processing to determine whether the dataset(s) may beidentified). The validations rules may be accessed/obtained by thedataset engine 114 from one or more locations and/or integrated into thedataset engine 114. The validation rules may be static or dynamic (e.g.,rules which must be met may change based on the information containedwithin the file name and/or metadata). In some embodiments, one or moreof the validation rules may be changed (e.g., via system update, viauser input).

In some embodiments, the dataset engine 114 may determine whether thedataset(s) to which a file is to be integrated can be identified basedon parsing the file name of the file. For example, the dataset engine114 may parse the file name of the file to determine/identify the filetype/type of data contained within the file (e.g., type/format of sensordata), specifics relating to the file/data contained within the file(e.g., sub-type, sensor channel), location(s) to which the datacontained within the file relates, object(s) to which the data containedwithin the file relates, date(s)/time(s) of the data contained withinthe file, user/organization associated with the file, and/or otherinformation which may be used to identify the dataset(s) to which thefile is to be integrated.

For a binary file (file including binary data), at least some of themetadata (for identifying the dataset(s) to which the file is to beintegrated), may be determined/identified based on decoding one or moreportions of the binary data. For example, the first portion of the file(e.g., the first binary portion of a certain size) may be streamed anddecoded. The decoded information may be analyzed to determine themetadata embedded within the file and/or to validate/identify the datacontained within the file. In some embodiments, processing of the binarydata within the file may be separate (e.g., performed in a separatepass) from parsing the file name for identifying the dataset(s).

If the dataset(s) to which a file is to be integrated cannot beidentified, the file may be designated as a non-integratable file. Forexample, the file may be tagged/marked as a file which cannot be routedfor integration into a dataset.

In various embodiments, the request engine 116 may be configured to,responsive to the dataset not being identifiable (by the dataset engine114), request information needed to identify the dataset. The requestengine 116 may identify and request from a user/system the informationneeded to identify the dataset to which the file is to be integrated. Insome embodiments, a particular set of information may be required toidentify the dataset into which the file is to be integrated. Therequest engine 116 may identify, among the particular set ofinformation, which information has not been provided by the file name,the metadata, and/or other information associated with the file (e.g.,provided via user input). In some embodiments, the information requiredto identify the dataset may be dynamically determined/managed. That is,the information required to identify the dataset may change based on theinformation provided by the file name, the metadata, and otherinformation associated with the file (e.g., based on having informationof type A about a file, the request engine 116 may request informationof types B and C; based on having information of type D about a file,the request engine 116 may request information of types E). In someembodiments, the request engine 116 may request the information neededto identify the dataset through one or more user interfaces. Such userinterfaces may be referred to as a file integration interface.

In some embodiments, the request engine 116 may provide one or morealerts indicating that the dataset for the file could not be identified.For example, an error icon, a status indicator, an error message, and/orother visuals may be displayed (e.g., within a file integrationinterface) for the file for which the dataset could not be identified.The error icon may indicate (based on shape and/or color) that thedataset could not be identified (e.g., the file could not be validatedfor integration) based on the file name and/or the metadata. The statusindicator may state the current status of the file-whether the datasetcan be/has been identified (e.g., the file was validated forintegration), whether the dataset cannot/has not be identified (e.g.,the file has not been validated), whether the file has been integratedinto the dataset, and/or other status identifying descriptions regardingthe file. The error message may display one or more reasons why thedataset could not be identified, which information has been properlyreceived/processed to identify the dataset, and/or other informationrelating to identifying the dataset for the file. In some embodiments,the error message may be displayed in response to a user interactingwith one or more portions of the file integration interface. Forexample, the error message may be displayed in response to a userclicking on/hovering over the error icon or the status indicator.

In some embodiments, the request engine 116 may request the informationneeded to identify the dataset by displaying the information needed toidentify the dataset within the file integration interface. For example,the information used/needed to identify the dataset may be displayedwithin the error message and/or other visuals presented through the fileintegration interface. In some embodiments, the information used/neededto identify the dataset may be displayed in response to a user'sinteraction with one or more portions of the file integration interface.For example, the file integration interface may include one or moreoptions through which information about individual files may bepresented. Based on a user's interaction with such options, the fileintegration interface may display the information used/needed toidentify the dataset. The file integration interface may enable a userto change one or more of information used/needed to identify thedataset. For example, the file integration interface may enable a useradd a particular property/attribute of the file, which was not includedin the file name or the metadata of the file, and/or change a particularproperty/attribute of the file extracted from the file name or themetadata of the file. Such information may be part of the informationused/needed to identify the dataset. In some embodiments, the requestengine 116 may persist the user added/changed information for a file bymaking changes to the file name and/or the metadata of the file.

In some embodiments, the file integration interface may provide otherviews/options relating to the files. For example, the file integrationinterface may provide a listing of other files that have been determinedto be integrated into one or more datasets and/or other files that havebeen integrated into one or more datasets. For example, the fileintegration interface may provide a listing of (1) files to beintegrated (e.g., files uploaded for integration), and (2) files thathave been integrated into their respective datasets (e.g., filespreviously uploaded and integrated into datasets). The file integrationinterface may provide information about the integrated files (such aswhen the file was received for integration, when the file wasintegrated, into what dataset the file was integrated, where the datasetis located) and/or may provide options for a user to view/retrieve(e.g., download) previously integrated files. Options to retrievepreviously integrated files may include options to retrieve the rawversion of the file that was received for integration and/or thetransformed version of the file that was integrated into the datasets.

As another example, the file integration interface may provide one ormore previews of a file. A preview of a file may include a view of someor all of raw data contained within the file, a view of some or all ofdata contained within the file that have been processed (e.g., decoded,transformed), and/or other views of the file. For example, datacontained within a file may be processed, formatted in one or morecharts, graphically rendered, and/or presented for viewing. In someembodiments, the processing of the file may be performed by the same orsimilar operations used to integrate the file into its dataset(s). Auser may use a preview of a file to view and/or confirm its contentsbefore the file is routed for integration into its dataset(s). Provisionof other views/options relating to the files are contemplated.

In various embodiments, the routing engine 118 may be configured to,responsive to the dataset(s) being identifiable, route the file forintegration into the dataset(s). Routing a file for integration into adataset may include providing/passing the file to one or moreprocesses/services/computing systems that performs the integrationand/or marking/tagging the file to be provided/passed to suchprocesses/services/computing systems. Integration of the file intodataset(s) may include transformation (e.g., extraction, processing,manipulation, modification, enhancement, combination) of data containedin the file by one or more operations. One or more such operations maybe arranged within a pipeline of operations for integrating files intodatasets.

For example, responsive to a given dataset being identified as thedataset to which the file is to be integrated, the routing engine 118may prompt a user to confirm the routing of the file for integrationinto the given dataset. Based on the user's confirmation, the file maybe routed for integration into the given dataset. For example, the fileintegration interface may provide one or more options for a user toprocess/route a single file or multiple files, for which the dataset(s)have been identified, for integration into the appropriate dataset(s).In some embodiments, the file integration interface may provide one ormore messages indicating a file is ready to be integrated into itsdataset(s). In some embodiments, one or more confirmations (e.g., viathe file integration interface, via electronic message, such as email)regarding the file/status of the file may be provided to one or moreusers/computing systems (e.g., user/computing system that provided thefile, user/system that integrates the file into the dataset(s)). In someembodiments, the file integration interface may enable a user toreattempt an integration of a file based on a failure of a prior attemptto integrate the file into its dataset(s).

FIG. 2 illustrates an example file naming convention 200 for a file tobe integrated into a dataset. The file naming convention 200 may providea framework for naming a file to describe data contained within thefile, how the file relates to other files, and/or other informationwhich may be used to identify the dataset(s) to which the file is to beintegrated. The file naming convention 200 is provided merely as anexample and, naturally, the arrangement and configuration of file namingconvention may vary depending on the implementation. Thus, depending onthe implementation, the file naming convention may include additional,alternative, and/or different structures.

The file naming convention 200 may split a file name into multiplesections. For example, as shown in FIG. 2, the file naming convention200 may split a file name into four sections: (1) type, (2) sub-type,(3) other information, and (4) file type. The type section of the filenaming convention 200 may define the type/format of the data containedwithin the file. The sub-type section of the file naming convention 200may define a more detailed information about the data type/specificsrelating to the data contained within the file. The other informationsection of the file naming convention 200 may define other informationused to identify the dataset(s) to which the file is to be integrated.For example, the other information section of the file naming convention200 may define one or more of location(s) of the data, object(s) towhich the data relates, date(s)/time(s) of the data (e.g., startdate/time, end date/time), user/organization, and/or other informationwhich may be used to identify the dataset(s) to which the file is to beintegrated. The other information section of the file naming convention200 may be sub-divided. The file type of the file naming convention 200may define the format of the file (e.g., whether the file includes/isincluded within an archive file).

In some embodiments, different sections of the file naming convention200 may be restricted to a certain length/number of characters. In someembodiments, different sections of the file naming convention 200 mayprovide for the types of characters which may be allowed within thedifferent sections. In some embodiments, different sections of the filenaming convention 200 may be separated by one or more characters (e.g.,separated by a dash “-”). Other file naming conventions for use invalidating data for integration are contemplated.

FIG. 3 illustrates an example user interface 300 for integrating a fileinto a dataset. In various embodiments, the user interface 300 may beaccessed through a software application running on a computing device(e.g., computers, mobile phones, tablets, etc.) that includes one ormore processors and memory. For example, the user interface 300 may beaccessible through a web browser. In another example, the user interface300 may be provided through a data analysis application. In yet anotherexample, the user interface 300 may be provided as a service over anetwork (e.g., software as a service). Depending on the computingdevice, the user may be able to interact with the user interface 300using various input devices (e.g., keyboard, mouse, etc.) and/ortouch/gestures. The user interface 300 is provided merely as an exampleand, naturally, the arrangement and configuration of such userinterfaces can vary depending on the implementation. Thus, depending onthe implementation, the user interface 300 may include additionalfeatures and/or alternative features. The user interface 300 mayinclude/enable one or more functionalities of the interface(s) describedabove with respect to the computing system 102/components of thecomputing system 102.

The user interface 300 may include an organization section 302, apending files section 304, and previous files section 306. Theorganization section 302 may provide descriptions of informationprovided within the pending files section 304 and the previous filessection 306, such as file name, property of the file (e.g., size, user,organization, one or more information contained within filename/metadataof the file), status of the file, and/or other descriptions. In someembodiments, a user may interact with the organization section 302 todisplay different types of descriptions, change the ordering of thedescriptions, and/or sort the listings of files within the pending filessection 304 and the previous files section 306 based on one or more ofthe descriptions within the organization section 302.

The pending files section 304 may provide a listing of files that are tobe integrated into one or more datasets. The pending files section 304may display information on whether the files are ready to be integratedinto the datasets. For example, the status of the respective files mayindicate that the files are ready to be integrated into their respectivedataset(s) by displaying the term “validated” or other terms/words, andmay indicate that the files are not ready to be integrated into theirrespective dataset(s) by displaying the term “not validated” or otherterms/words. The pending files section 304 may display information onwhether the files are ready to be integrated into the datasets usingicons (e.g., ready icon, error icon), messages (e.g., ready message,error message), and/or other visuals. For example, an error message maydisplay one or more reasons why the dataset could not be identified,which information has been properly received/processed to identify thedataset, and/or other information relating to identifying the datasetfor the file. In some embodiments, the error message may be displayed inresponse to a user interacting with one or more portions of the userinterface 300. For example, the error message may be displayed inresponse to a user clicking on/hovering over an error icon or a statusfor a file.

The user interface 300 may display information used/needed to identifythe dataset(s) to which a file is to be integrated. For example, theinformation used/needed to identify the dataset(s) may be displayedwithin the error message and/or other visuals presented through the userinterface 300. In some embodiments, the information used/needed toidentify the dataset(s) may be displayed in response to a user'sinteraction with one or more portions of the user interface 300. Forexample, the user interface 300 may include options 308 through whichinformation about individual files may be presented. Based on a user'sinteraction with the options 308, the user interface 300 may display(e.g., below the file name) the information used/needed to identify thedataset(s).

The user interface 300 may enable a user to change one or more ofinformation used/needed to identify the dataset(s). For example, theuser interface 300 may enable a user add a particular property/attributeof the file, which was not included in the file name or the metadata ofthe file, and/or change a particular property/attribute of the fileextracted from the file name or the metadata of the file. For example, auser may click on a particular information (e.g., Info A, Info B, InfoC, Info D, Info E) and define/change the particular information. In someembodiments, the user interface 300 may provide suggestions for a user'schanging of information. For example, responsive to a user's clicking onthe term “Info A,” the user interface 300 may provide a dropdown menufrom which particular information may be selected by the user and/or theuser interface 300 may prefill/suggest particular information to be usedfor “Info A.” In some embodiments, the user added/changed informationfor a file may be persisted through changes to the file name and/or themetadata of the file.

The user interface 300 may provide options 310 for a user toprocess/route individual files for integration into the appropriatedataset(s). The user interface 300 may provide an option 312 for a userto process/route multiple files (batch processing) for integration intothe appropriate dataset(s). In some embodiments, one or more of theoptions 310, 312 may be deactivated (e.g., greyed-out) in response toone or more of the files not being validated for integration. In someembodiments, one or more users (e.g., administrative users) may beprovided with an option to force integrate (e.g., force upload/processfor integration) a file into its dataset(s). The user interface 300 mayprovide options 314 for a user to remove files from dataset integration.

The user interface 300 may provide an option 316 for a user to add filesfor integration into dataset(s). In some embodiments, a user may addfiles for integration into dataset(s) by dragging and dropping the filesto one or more portions of the user interface 300 (e.g., dragging anddropping file into the pending files section 304). In some embodiments,one or more metadata/characteristics/properties of a file relating toits integration into dataset(s) may be defined when a user adds the filefor integration. Such information may be used to determine that the fileis to be integrated into a dataset and/or identify the dataset(s) towhich the file is to be integrated.

The previous files section 306 may provide a listing of files that havebeen integrated into one or more datasets. The status of the fileslisted in the previous files section 306 may indicate that the fileshave been integrated into dataset(s) (e.g., via the term “fileintegrated,” or other terms/words). The status of the files may provideother information about the individual files, such as the identificationof the dataset(s) to which the file was integrated, the location of thedataset(s), where the file was received, when the file was received,when the file was integrated, and/or other information. The userinterface 300 may provide options 318 for a user to view/retrieve (e.g.,download) previously integrated files. The options 308 may enable a userto retrieve the raw version of the file that was received forintegration and/or the transformed version of the file that wasintegrated into the dataset(s).

FIG. 4 illustrates a flowchart of an example method 400, according tovarious embodiments of the present disclosure. The method 400 may beimplemented in various environments including, for example, theenvironment 100 of FIG. 1. The operations of method 400 presented beloware intended to be illustrative. Depending on the implementation, theexample method 400 may include additional, fewer, or alternative stepsperformed in various orders or in parallel. The example method 400 maybe implemented in various computing systems or devices including one ormore processors.

At block 402, a file to be integrated into a dataset may be determined.The file may be characterized by a file name and metadata. At block 404,whether the dataset can be identified based on the file name and themetadata may be determined. At block 406, responsive to the dataset notbeing identifiable, information needed to identify the dataset may berequested. At block 408, responsive to the dataset being identifiable,the file may be routed for integration into the dataset.

Hardware Implementation

The techniques described herein are implemented by one or morespecial-purpose computing devices. The special-purpose computing devicesmay be hard-wired to perform the techniques, or may include circuitry ordigital electronic devices such as one or more application-specificintegrated circuits (ASICs) or field programmable gate arrays (FPGAs)that are persistently programmed to perform the techniques, or mayinclude one or more hardware processors programmed to perform thetechniques pursuant to program instructions in firmware, memory, otherstorage, or a combination. Such special-purpose computing devices mayalso combine custom hard-wired logic, ASICs, or FPGAs with customprogramming to accomplish the techniques. The special-purpose computingdevices may be desktop computer systems, server computer systems,portable computer systems, handheld devices, networking devices or anyother device or combination of devices that incorporate hard-wiredand/or program logic to implement the techniques.

Computing device(s) are generally controlled and coordinated byoperating system software, such as iOS, Android, Chrome OS, Windows XP,Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix,Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatibleoperating systems. In other embodiments, the computing device may becontrolled by a proprietary operating system. Conventional operatingsystems control and schedule computer processes for execution, performmemory management, provide file system, networking, I/O services, andprovide a user interface functionality, such as a graphical userinterface (“GUI”), among other things.

FIG. 5 is a block diagram that illustrates a computer system 500 uponwhich any of the embodiments described herein may be implemented. Thecomputer system 500 includes a bus 502 or other communication mechanismfor communicating information, one or more hardware processors 504coupled with bus 502 for processing information. Hardware processor(s)504 may be, for example, one or more general purpose microprocessors.

The computer system 500 also includes a main memory 506, such as arandom access memory (RAM), cache and/or other dynamic storage devices,coupled to bus 502 for storing information and instructions to beexecuted by processor 504. Main memory 506 also may be used for storingtemporary variables or other intermediate information during executionof instructions to be executed by processor 504. Such instructions, whenstored in storage media accessible to processor 504, render computersystem 500 into a special-purpose machine that is customized to performthe operations specified in the instructions.

The computer system 500 further includes a read only memory (ROM) 508 orother static storage device coupled to bus 502 for storing staticinformation and instructions for processor 504. A storage device 510,such as a magnetic disk, optical disk, or USB thumb drive (Flash drive),etc., is provided and coupled to bus 502 for storing information andinstructions.

The computer system 500 may be coupled via bus 502 to a display 512,such as a cathode ray tube (CRT) or LCD display (or touch screen), fordisplaying information to a computer user. An input device 514,including alphanumeric and other keys, is coupled to bus 502 forcommunicating information and command selections to processor 504.Another type of user input device is cursor control 516, such as amouse, a trackball, or cursor direction keys for communicating directioninformation and command selections to processor 504 and for controllingcursor movement on display 512. This input device typically has twodegrees of freedom in two axes, a first axis (e.g., x) and a second axis(e.g., y), that allows the device to specify positions in a plane. Insome embodiments, the same direction information and command selectionsas cursor control may be implemented via receiving touches on a touchscreen without a cursor.

The computing system 500 may include a user interface module toimplement a GUI that may be stored in a mass storage device asexecutable software codes that are executed by the computing device(s).This and other modules may include, by way of example, components, suchas software components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables.

In general, the word “module,” as used herein, refers to logic embodiedin hardware or firmware, or to a collection of software instructions,possibly having entry and exit points, written in a programminglanguage, such as, for example, Java, C or C++. A software module may becompiled and linked into an executable program, installed in a dynamiclink library, or may be written in an interpreted programming languagesuch as, for example, BASIC, Perl, or Python. It will be appreciatedthat software modules may be callable from other modules or fromthemselves, and/or may be invoked in response to detected events orinterrupts. Software modules configured for execution on computingdevices may be provided on a computer readable medium, such as a compactdisc, digital video disc, flash drive, magnetic disc, or any othertangible medium, or as a digital download (and may be originally storedin a compressed or installable format that requires installation,decompression or decryption prior to execution). Such software code maybe stored, partially or fully, on a memory device of the executingcomputing device, for execution by the computing device. Softwareinstructions may be embedded in firmware, such as an EPROM. It will befurther appreciated that hardware modules may be comprised of connectedlogic units, such as gates and flip-flops, and/or may be comprised ofprogrammable units, such as programmable gate arrays or processors. Themodules or computing device functionality described herein arepreferably implemented as software modules, but may be represented inhardware or firmware. Generally, the modules described herein refer tological modules that may be combined with other modules or divided intosub-modules despite their physical organization or storage.

The computer system 500 may implement the techniques described hereinusing customized hard-wired logic, one or more ASICs or FPGAs, firmwareand/or program logic which in combination with the computer systemcauses or programs computer system 500 to be a special-purpose machine.According to one embodiment, the techniques herein are performed bycomputer system 500 in response to processor(s) 504 executing one ormore sequences of one or more instructions contained in main memory 506.Such instructions may be read into main memory 506 from another storagemedium, such as storage device 510. Execution of the sequences ofinstructions contained in main memory 506 causes processor(s) 504 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “non-transitory media,” and similar terms, as used hereinrefers to any media that store data and/or instructions that cause amachine to operate in a specific fashion. Such non-transitory media maycomprise non-volatile media and/or volatile media. Non-volatile mediaincludes, for example, optical or magnetic disks, such as storage device510. Volatile media includes dynamic memory, such as main memory 506.Common forms of non-transitory media include, for example, a floppydisk, a flexible disk, hard disk, solid state drive, magnetic tape, orany other magnetic data storage medium, a CD-ROM, any other optical datastorage medium, any physical medium with patterns of holes, a RAM, aPROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunctionwith transmission media. Transmission media participates in transferringinformation between non-transitory media. For example, transmissionmedia includes coaxial cables, copper wire and fiber optics, includingthe wires that comprise bus 502. Transmission media can also take theform of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 504 for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 500 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 502. Bus 502 carries the data tomain memory 506, from which processor 504 retrieves and executes theinstructions. The instructions received by main memory 506 may retrievesand executes the instructions. The instructions received by main memory506 may optionally be stored on storage device 510 either before orafter execution by processor 504.

The computer system 500 also includes a communication interface 518coupled to bus 502. Communication interface 518 provides a two-way datacommunication coupling to one or more network links that are connectedto one or more local networks. For example, communication interface 518may be an integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 518 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN (or WANcomponent to communicated with a WAN). Wireless links may also beimplemented. In any such implementation, communication interface 518sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

A network link typically provides data communication through one or morenetworks to other data devices. For example, a network link may providea connection through local network to a host computer or to dataequipment operated by an Internet Service Provider (ISP). The ISP inturn provides data communication services through the world wide packetdata communication network now commonly referred to as the “Internet”.Local network and Internet both use electrical, electromagnetic oroptical signals that carry digital data streams. The signals through thevarious networks and the signals on network link and throughcommunication interface 518, which carry the digital data to and fromcomputer system 500, are example forms of transmission media.

The computer system 500 can send messages and receive data, includingprogram code, through the network(s), network link and communicationinterface 518. In the Internet example, a server might transmit arequested code for an application program through the Internet, the ISP,the local network and the communication interface 518.

The received code may be executed by processor 504 as it is received,and/or stored in storage device 510, or other non-volatile storage forlater execution.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors comprising computer hardware. The processes and algorithmsmay be implemented partially or wholly in application-specificcircuitry.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure. The foregoing description details certainembodiments of the invention. It will be appreciated, however, that nomatter how detailed the foregoing appears in text, the invention can bepracticed in many ways. As is also stated above, it should be noted thatthe use of particular terminology when describing certain features oraspects of the invention should not be taken to imply that theterminology is being re-defined herein to be restricted to including anyspecific characteristics of the features or aspects of the inventionwith which that terminology is associated. The scope of the inventionshould therefore be construed in accordance with the appended claims andany equivalents thereof.

Engines, Components, and Logic

Certain embodiments are described herein as including logic or a numberof components, engines, or mechanisms. Engines may constitute eithersoftware engines (e.g., code embodied on a machine-readable medium) orhardware engines. A “hardware engine” is a tangible unit capable ofperforming certain operations and may be configured or arranged in acertain physical manner. In various example embodiments, one or morecomputer systems (e.g., a standalone computer system, a client computersystem, or a server computer system) or one or more hardware engines ofa computer system (e.g., a processor or a group of processors) may beconfigured by software (e.g., an application or application portion) asa hardware engine that operates to perform certain operations asdescribed herein.

In some embodiments, a hardware engine may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware engine may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware engine may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware engine may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware enginemay include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwareengines become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware engine mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) may be driven by cost and time considerations.

Accordingly, the phrase “hardware engine” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented engine” refers to a hardware engine. Consideringembodiments in which hardware engines are temporarily configured (e.g.,programmed), each of the hardware engines need not be configured orinstantiated at any one instance in time. For example, where a hardwareengine comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware engines) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware engine at one instance oftime and to constitute a different hardware engine at a differentinstance of time.

Hardware engines can provide information to, and receive informationfrom, other hardware engines. Accordingly, the described hardwareengines may be regarded as being communicatively coupled. Where multiplehardware engines exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware engines. In embodiments inwhich multiple hardware engines are configured or instantiated atdifferent times, communications between such hardware engines may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware engines have access.For example, one hardware engine may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware engine may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware engines may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented enginesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented engine” refers to ahardware engine implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented engines. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented engines may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented engines may be distributed across a number ofgeographic locations.

Language

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the subject matter has been described withreference to specific example embodiments, various modifications andchanges may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the subject matter may be referred to herein, individually orcollectively, by the term “invention” merely for convenience and withoutintending to voluntarily limit the scope of this application to anysingle disclosure or concept if more than one is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

It will be appreciated that an “engine,” “system,” “data store,” and/or“database” may comprise software, hardware, firmware, and/or circuitry.In one example, one or more software programs comprising instructionscapable of being executable by a processor may perform one or more ofthe functions of the engines, data stores, databases, or systemsdescribed herein. In another example, circuitry may perform the same orsimilar functions. Alternative embodiments may comprise more, less, orfunctionally equivalent engines, systems, data stores, or databases, andstill be within the scope of present embodiments. For example, thefunctionality of the various systems, engines, data stores, and/ordatabases may be combined or divided differently.

“Open source” software is defined herein to be source code that allowsdistribution as source code as well as compiled form, with awell-publicized and indexed means of obtaining the source, optionallywith a license that allows modifications and derived works.

The data stores described herein may be any suitable structure (e.g., anactive database, a relational database, a self-referential database, atable, a matrix, an array, a flat file, a documented-oriented storagesystem, a non-relational No-SQL system, and the like), and may becloud-based or otherwise.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, engines, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Although the invention has been described in detail for the purpose ofillustration based on what is currently considered to be the mostpractical and preferred implementations, it is to be understood thatsuch detail is solely for that purpose and that the invention is notlimited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present invention contemplates that, to theextent possible, one or more features of any embodiment can be combinedwith one or more features of any other embodiment.

The invention claimed is:
 1. A system comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the system to perform: determining a fileto be integrated into a dataset, the file characterized by a file nameand metadata; determining that at least one of the file name or themetadata comprises first partial information for identifying thedataset; determining that the dataset is not identifiable based solelyon the first partial information; responsive to the dataset not beingidentifiable based solely on the first partial information, dynamicallydetermining that second partial information indicative of one or moreattributes of the file that are not determinable from the file name orthe metadata is needed to identify the dataset; responsive todynamically determining that the second partial information is needed toidentify the dataset, requesting the second partial information;receiving the second partial information; determining that the datasetis identifiable based on the combination of the first partialinformation and the second partial information; and responsive to thedataset being identifiable based on the combination of the first partialinformation and the second partial information, routing the file forintegration into the dataset.
 2. The system of claim 1, wherein at leastsome of the metadata is identified based on parsing the file name. 3.The system of claim 1, wherein the file includes binary data, and atleast some of the metadata is identified based on decoding a portion ofthe binary data.
 4. The system of claim 1, wherein requesting theinformation needed to identify the dataset includes displaying theinformation needed to identify the dataset within a file integrationinterface.
 5. The system of claim 4, wherein the file integrationinterface provides a preview of the file.
 6. The system of claim 4,wherein the file integration interface provides a view of informationused to identify the dataset.
 7. The system of claim 6, wherein the fileintegration interface enables a user to change the information used toidentify the dataset.
 8. A method implemented by a computing systemincluding one or more processors and storage media storingmachine-readable instructions, wherein the method is performed using theone or more processors, the method comprising: determining a file to beintegrated into a dataset, the file characterized by a file name andmetadata; determining that at least one of the file name or the metadatacomprises first partial information for identifying the dataset;determining that the dataset is not identifiable based solely on thefirst partial information; responsive to the dataset not beingidentifiable based solely on the first partial information, dynamicallydetermining that second partial information indicative of one or moreattributes of the file that are not determinable from the file name orthe metadata is needed to identify the dataset; responsive todynamically determining that the second partial information is needed toidentify the dataset, requesting the second partial information;receiving the second partial information; determining that the datasetis identifiable based on the combination of the first partialinformation and the second partial information; and responsive to thedataset being identifiable based on the combination of the first partialinformation and the second partial information, routing the forintegration into the dataset.
 9. The method of claim 8, wherein at leastsome of the metadata is identified based on parsing the file name. 10.The method of claim 8, wherein the file includes binary data, and atleast some of the metadata is identified based on decoding a portion ofthe binary data.
 11. The method of claim 8, wherein requesting theinformation needed to identify the dataset includes displaying theinformation needed to identify the dataset within a file integrationinterface.
 12. The method of claim 11, wherein the file integrationinterface provides a preview of the file.
 13. The method of claim 11,wherein the file integration interface provides a view of informationused to identify the dataset.
 14. The method of claim 13, wherein thefile integration interface enables a user to change the information usedto identify the dataset.
 15. A non-transitory computer readable mediumcomprising instructions that, when executed, cause one or moreprocessors to perform: determining a file to be integrated into adataset, the file characterized by a file name and metadata; determiningthat at least one of the file name or the metadata comprises firstpartial information for identifying the dataset; determining that thedataset is not identifiable based solely on the first partialinformation; responsive to the dataset not being identifiable basedsolely on the first partial information, dynamically determining thatsecond partial information indicative of one or more attributes of thefile that are not determinable from the file name or the metadata isneeded to identify the dataset; responsive to dynamically determiningthat the second partial information is needed to identify the dataset,requesting the second partial information; receiving the second partialinformation; determining that the dataset is identifiable based on thecombination of the first partial information and the second partialinformation; and responsive to the dataset being identifiable based onthe combination of the first partial information and the second partialinformation, routing the file for integration into the dataset.
 16. Thenon-transitory computer readable medium of claim 15, wherein at leastsome of the metadata is identified based on parsing the file name. 17.The non-transitory computer readable medium of claim 15, wherein thefile includes binary data, and at least some of the metadata isidentified based on decoding a portion of the binary data.
 18. Thenon-transitory computer readable medium of claim 15, wherein requestingthe information needed to identify the dataset includes displaying theinformation needed to identify the dataset within a file integrationinterface.
 19. The non-transitory computer readable medium of claim 18,wherein the file integration interface provides a preview of the file.20. The non-transitory computer readable medium of claim 18, wherein thefile integration interface provides a view of information used toidentify the dataset.